-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat!: add burned outputs #4364
feat!: add burned outputs #4364
Conversation
d41eaf0
to
4fd1a59
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice looks good - few minor comments.
Will run a test.
base_layer/core/src/transactions/transaction_components/output_type.rs
Outdated
Show resolved
Hide resolved
base_layer/core/src/transactions/transaction_components/transaction_kernel.rs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy to merge. Please create an issue for the missing unit tests
/// THis function checks the total burned sum in the header ensuring that every burned output is counted in the total | ||
/// sum. | ||
#[allow(clippy::mutable_key_type)] | ||
pub fn check_total_burned(body: &AggregateBody) -> Result<(), ValidationError> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need some unit tests to prove this picks up the errors
@SWvheerden Tested via grpc. Base node accepted the transaction into the mempool but rejected the block
|
Description
This Pr adds in the ability to create burned outputs.
There will be a follow-up PR addressing the kernel mutability as currently the fields are mutable and need to be signed to block mutability, see: #4365.
For added reasoning why this is needed see RFC: tari-project/rfcs#10
Full testing of this is also blocked by: #4360
How Has This Been Tested?
Unit and integration tests.